View MB86977PFV-G-BND_1934737.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

ds04-22114-1e fujitsu semiconductor data sheet communication control assp ip packet forwarding engine mb86977 n description the mb86977 is an lsi that enables processes that previously were handled through software, such as packet- destination transferring and filtering, to be handled through hardware, thereby achieving a full wire speed bi- directional lan-wan throughput of 100 mbps. the ip forwarding can be applied to both ipv4 and ipv6 packets at full wire speed.the layer 3/4 filtering capabilities enables application of basic security policies, and also makes it possible to build demilitarized zones (d.m.z.) for servers to be accessed directly from the www without intervention of software. out of a total of four mac interfaces, two are used for internal segments (i.e. lan0,lan1), one as a d.m.z. port, and the remaining as a wan port. the d.m.z.interface may be configured as an extra internal segment (i.e. lan2)if desired. the layer 2 switch can switch packets from internal segments (lan0, lan1 and lan2) based on their mac addresses. in addition, real-time applications such as streaming media flows and voip streams can be prioritized by the priority control function. the mb86977 offers the ideal solution for superior performance required by network appliances such as broadband routers. n features 1. built-in high performance ip forwarding engine fujitsu/fls express forwarding (fef) engine ip packet forwarding ? routing operations such as ethernet mac address replacement, ttl reduction and checksum generation done in hardware ? supports both ipv4 and ipv6 ? supports pppoe tunneling and ipv6 over ipv4 tunneling at wan interface (continued) n pac k ag e 208-pin plastic lqfp (fpt-208p-m06)
mb86977 2 (continued) nat (napt) ? nat operations such as ip address replacement, transport layer port number replacement, and checksum generation done in hardware ? supports pppoe tunneling and ipv6 over ipv4 tunneling at wan interface ? supports ipv4 only. layer 3/4 filtering ? filtering based on ip address (dst and/or src, supports both ipv4/ipv6) ? filtering based on tcp/udp port number (supports tcp and ack flag) ? filtering based on combinations of ip address and tcp port number in tcp connections for both ipv4 and ipv6. ? filtering based on icmp type ? filtering based on protocol type (type field in ethernet) ? supports pppoe discovery stage /session stage filtering ? supports ah (authentication header) type vpn packet filtering by layer 3/4 information ? supports esp (encapsulating security payload) type vpn packets filtering by ip address ? filtering can be applied independently per each port (lan,d.m.z., wan) ? supports max 64x2 (inbound and outbound) filter table entries ? supports filter logging packet prioritizing function ? prioritization based on combination of ipv4 address and udp port number ? prioritization based on combination of ipv4 address and tos field ? prioritization based on combination of ipv4 address, tos field and udp port number ? prioritization based on combination of ipv6 address, traffic class and flow label ? supports qos mapping tos field note: the fef supports only dix type ethernet frames, and does not support ieee802.1 llc type frames and ieee802.1q vlan tagged frames (these frames, when received, will be sent to the host). achieving a full wire rate bi-directional throughput of 100 mbps at 50 mhz operation. 2. layer 2 (mac) functions ? four integrated ieee802.3 compliant 10/100baset/tx mac ports ? port selectable rmii/mii interface (supports both full duplex and half duplex) ? smi interface for phy device configuration ? supports auto negotiation ? supports ieee802.3x flow control ? supports back pressure for half duplex mode ? integrated sram for packet buffering (pram) ? store-and-forward switching method ? mac address table up to 50 entries ? mac address auto learning and aging 3. host interface ? 32 bit-width sram host interface ? bigendian/littleendian configurable 4. other features ? 208-pin plastic lqfp package
mb86977 3 n pin assignment (continued) pin no. pin name pin no. pin name pin no. pin name pin no. pin name 1 tdout 36 dq18 71 col_0 106 vss 2 sdo1 37 dq19 72 tx_clk_0 107 tx_en_d 3 sdo238dq2073 vss108txd_d [0] 4 sdo3 39 vdde 74 rx_dv_0 109 txd_d [1] 5 sdo4 40 vss 75 rxd_0 [0] 110 txd_d [2] 6 sdo5 41 vddi 76 rxd_0 [1] 111 txd_d [3] 7 sdo6 42 dq21 77 rxd_0 [2] 112 vdde 8 int_ 43 dq22 78 rxd_0 [3] 113 vss 9 vdde 44 dq23 79 rx_er_0 114 vddi 10 vss 45 dq24 80 rx_clk_0 115 vdde 11 vddi 46 dq25 81 vdde 116 vss 12 vdde 47 dq26 82 vss 117 vddi 13 vss 48 dq27 83 vddi 118 crs_dv_d 14 vddi 49 dq28 84 crs_dv_1 119 col_d 15 dq0 50 dq29 85 col_1 120 tx_clk_d 16 dq1 51 dq30 86 tx_clk_1 121 vss 17 dq2 52 dq31 87 vss 122 rx_dv_d 18 dq3 53 vdde 88 rx_dv_1 123 rxd_d [0] 19 dq4 54 vss 89 rxd_1 [0] 124 rxd_d [1] 20 dq5 55 vddi 90 rxd_1 [1] 125 rxd_d [2] 21 dq6 56 vdde 91 rxd_1 [2] 126 rxd_d [3] 22 dq7 57 vss 92 rxd_1 [3] 127 rx_er_d 23 dq8 58 vddi 93 rx_er_1 128 rx_clk_d 24 dq9 59 tx_en_0 94 rx_clk_1 129 vdde 25 dq10 60 txd_0 [0] 95 vdde 130 vss 26 vdde 61 txd_0 [1] 96 vss 131 vddi 27 vss 62 txd_0 [2] 97 vddi 132 crs_dv_w 28 vddi 63 txd_0 [3] 98 vdde 133 col_w 29 dq11 64 vdde 99 vss 134 tx_clk_w 30 dq12 65 vss 100 vddi 135 vss 31 dq13 66 vddi 101 tx_en_1 136 rx_dv_w 32 dq14 67 vdde 102 txd_1 [0] 137 rxd_w [0] 33 dq15 68 vss 103 txd_1 [1] 138 rxd_w [1] 34 dq16 69 vddi 104 txd_1 [2] 139 rxd_w [2] 35 dq17 70 crs_dv_0 105 txd_1 [3] 140 rxd_w [3]
mb86977 4 (continued) pin no. pin name pin no. pin name pin no. pin name pin no. pin name 141 rx_er_w 158 vddi 175 a4 192 sdi4 142 rx_clk_w 159 vdde 176 a5 193 sdi5 143 vdde 160 vss 177 a6 194 sdi6 144 vss 161 vddi 178 a7 195 vss 145 vddi 162 mdio 179 a8 196 xtck 146 vdde 163 vss 180 a9 197 vss 147 vss 164 ref_clk 181 a10 198 trst 148 vddi 165 vss 182 a11 199 tmode 149 tx_en_w 166 cs_ 183 a12 200 vpd 150 txd_w [0] 167 we_ 184 a13 201 tdin 151 txd_w [1] 168 re_ 185 srst_ 202 tclk 152 txd_w [2] 169 vdde 186 vdde 203 vdde 153 txd_w [3] 170 vss 187 vss 204 vss 154 vss 171 vddi 188 vddi 205 vddi 155 mdclk 172 sclk 189 sdi1 206 vdde 156 vdde 173 a2 190 sdi2 207 vss 157 vss 174 a3 191 sdi3 208 vddi
mb86977 5 n pin description host (sram) interface rmii interface note : the logical and of the tx_en and crs_dv signals indicate a collision during half duplex modes. pin no. pin name i/o function 173 to 184 a2 to a13 i address bus address input 15 to 25 29 to 38 42 to 52 dq0 to dq31 i/o data input/output data input/output (32 bit) 166 cs_ i chip select chip select input 167 we_ i write enable write operation enable signal (low enable) 168 re_ i read enable read operation enable signal (low enable) 8int_o interrupt interrupt indication (low enable) pin no. pin name i/o function 164 ref_clk i reference clock reference clock from the phy device. the frequency is 50 mhz for both 10 mbps and 100 mbps. 150, 151 108, 109 60, 61 102, 103 txd_w [1 : 0] txd_d [1 : 0] txd_0 [1 : 0] txd_1 [1 : 0] o transmit data the two bit data is transmitted to phy devices through this interface. synchronous with ref_clk. 149 107 59 101 tx_en_w tx_en_d tx_en_0 tx_en_1 o transmit enable active high signal indicates that tx data is valid.synchronous with ref_clk. 141 127 79 93 rx_er_w rx_er_d rx_er_0 rx_er_1 i receive error active high signal indicates that an invalid symbol has been detected within a received packet.this input is ignored when the crs_dv signal is inactive. 137, 138 123, 124 75, 76 89, 90 rxd_w [1 : 0] rxd_d [1 : 0] rxd_0 [1 : 0] rxd_1 [1 : 0] i receive data the two bit data is received from the phy device through this interface. 132 118 70 84 crs_dv_w crs_dv_d crs_dv_0 crs_dv_1 i carrier sense / receive data valid phy device inputs active high signal when the interface is receiving data. asynchronous assertion/deassertion by phy device upon carrier detection/carrier invalid.
mb86977 6 mii interface smi interface pin no. pin name i/o description 134 120 72 86 tx_clk_w tx_clk_d tx_clk_0 tx_clk_1 i tx clock this clock from the phy device provides the timing reference for transfer of tx_en and txd signals. the frequency is 25 mhz for 100 mbps, 2.5 mhz for 10 mbps. 150 to 153 108 to 111 60 to 63 102 to 105 txd_w [3 : 0] txd_d [3 : 0] txd_0 [3 : 0] txd_1 [3 : 0] o transmit data the nibble data is transmitted to phy devices through this interface. 149 107 59 101 tx_en_w tx_en_d tx_en_0 tx_en_1 o transmit enable active high signal indicates that tx data is valid. synchronous with tx_clk. 142 128 80 94 rx_clk_w rx_clk_d rx_clk_0 rx_clk_1 i rx clock this clock from the phy device provides the timing reference for reception. the frequency is 25 mhz for 100 mbps, 2.5 mhz for 10 mbps. 141 127 79 93 rx_er_w rx_er_d rx_er_0 rx_er_1 i receive error active high signal indicates that an invalid symbol has been detected within a received packet.this input is ignored when rx_dv signal of the same interface is inactive.these pins are used for both rmii and mii modes. 136 122 74 88 rx_dv_w rx_dv_d rx_dv_0 rx_dv_1 i receive data valid active high signal indicates that rxd is valid. 132 118 70 84 crs_dv_w crs_dv_d crs_dv_0 crs_dv_1 i carrier sense active high signal indicates that either the transmit or receive medium is not idle. it is not synchronous to any clock. these pins are used for both rmii and mii modes. 137 to 140 123 to 126 75 to 78 89 to 92 rxd_w [3 : 0] rxd_d [3 : 0] rxd_0 [3 : 0] rxd_1 [3 : 0] i receive data nibble data from the phy device.bits [1:0] are used for both mii and rmii modes. 133 119 71 85 col_w col_d col_0 col_1 i collision detect active high signal indicates that collision has been detected in half duplex mode. it is valid when tx_en is active. it is not synchronous to any clock. pin no. pin name i/o description 155 mdclk o management data clock smi clock to phys. 162 mdio i/o management data input/output smi data to/from phys.
mb86977 7 others pin no. pin name i/o description 185 srst_ i system reset system reset signal. 172 sclk i system clock system clock of this device. also used as host interface reference clock. 198 trst i input the h level. for any system operation, be sure to input a reset signal to this pin. (set the signal level to l and then to h) 199 201 202 tmode tdin tclk i input the h level. 9, 12, 26 39, 53, 56 64, 67, 81 95, 98, 112 115, 129, 143 146, 156, 159 169, 186, 203 206 vdde ? 3.3 v power supply pin. 11, 14, 28 41, 55, 58 66, 69, 83 97, 100, 114 117, 131, 145 148, 158, 161 171, 188, 205 208 vddi ? 1.8 v power supply pin. 10, 13, 27 40, 54, 57 65, 68, 73 82, 87, 96 99, 106, 113 116, 121, 130 135, 144, 147 154, 157, 160 163, 165, 170 187, 195, 197 204, 207 vss ? ground pins. 189 to 194 196 200 sdi1 to sdi6 xtck vpd ? ground pins. 1 2 to 7 tdout sdo1 to sdo6 nc leave this open.
mb86977 8 n block diagram (lan 0.1 d.m.z. wan) rmi/mii x 4 smi i/f sram i/f mac data bus : 64 bit mac control bus host i/f data bus : 32 bit host i/f control bus mac tx/rx unit mac control unit smi block receive/ transmit buffer switch block l2 lookup table lookup block classifier block for d.m.z., wan mac block host i/f block fef engine
mb86977 9 n block description 1. mac block the mac block transmits and receives packets through the rmii or mii interfaces, and performs layer 2 (mac) functions as defined in ieee 802.3. the mac block transfers the received frames to the switch block, and transmits frames received from the switch block to the output interface. 2. smi block the smi block gathers various information (such as full/half duplex, link status,10/100 base, etc.) by reading the phy device registers through the smi interface, and configures the phy device by writing through the smi interface. 3. switch block the switch block stores packets received from the mac block in rams (pram) , and transfers the packets to the destination interface based on the information acquired from the lookup block. 4. lookup block the lookup block looks up the mac address of the packet received from the mac block, and returns destination interface information to the switch block. 5. classifier block the classifier block is used to determine the priority of the packets to be transferred between the wan and d.m.z. ports. the packets can be classified into two priorities (high or low) by the classifier block. packets classified as high are placed in the high priority queue, and are processed by the switch block before the low priority packets. 6. host interface block the host interface block contains the fef engine and other minor blocks. the fef engine forwards packets between interfaces and transmits packets to/from the host. the host interface is also used to read/write from/ to the internal registers. when the mb86977 receives packets destined for the host, the host interface asserts an interrupt signal and specifies the information in the status register. the host transmits packets by writing a descriptor to an internal register with the information necessary to transmit. the host interface block has two 3k byte integrated dual port rams that can be randomly accessed for trans- mitting and receiving packets. the host interface can be accessed like a general-purpose sram.
mb86977 10 n functional description 1. fef engine-nat/ip forwarding function the fef engine-nat/ip forwarding macro accelerates nat transformation and ip forwarding through hardware, eliminating the use of software, i.e. host processing. up to 128 nat/ip forwarding connections, each defined by the parameters set in the nat/ip forwarding table, can be configured. these connections are the transmission paths that connect the wan and d.m.z. interfaces, the wan and lan interfaces, and the d.m.z. and lan interfaces-all at full wire speed. the ip forwarding and nat operations are briefly explained below. ip forwarding when both the destination and source ip addresses of an input packet matches one of the entries in the nat/ ip forwarding table, the packet is forwarded through hardware to the destination interface indicated by the matching entry. this transmission does not require host processing and is performed at full wire speed. if there is no entry in the nat/ip forwarding table that matches both ip addresses (destination and source ip address) of the input packet, the packet is sent to the host through the host interface. described below is the operation performed on the packet when ip forwarding is being applied: ? mac address replacement ?ttl subtraction ? ip header checksum recalculation ? ethernet frame crc recalculation ? transmission from the destination interface indicated as for ip forwarding, both ipv4 and ipv6 type packets can be processed. nat when the destination and source ip addresses and the destination and source tcp/udp port numbers of an input packet matches one of the entries in the nat/ip forwarding table, the hardware translates the address, replaces the port numbers, and forwards the packet to the destination interface, all according to the parameters defined by the matching entry. this transmission does not require host processing and is performed at full wire speed. if there is no entry in the nat/ip forwarding table that matches both ip addresses (destination and source ip address) and both tcp/udp port numbers of the input packet, the packet is sent to the host through the host interface. described below is the operation performed on the packet when nat is being applied: ? mac address replacement ?ttl subtraction ? ip address replacement ? ip header checksum recalculation ? tcp/udp port number replacement ? tcp/udp header checksum recalculation ? ethernet frame crc recalculation ? transmission from the destination interface indicated as for nat, only ipv4 type packets can be processed. ah and esp input packets are not subject to nat translations.these types of packets are sent to the host through the host interface.
mb86977 11 the nat/ip forwarding function is summarized in the illustration below. nat/ip forwarding function overview to cpu host interface block sram i/f tx buffer rx buffer when a match is found in the table when no match is found in the table fef- tx filter fef- rx filter switch block i/f to internal bus fef nat/ip forwarding
mb86977 12 2. fef engine-header processing function this device implements the processing of pppoe and ipv6 over ipv4 tunnel packets through hardware. when an input packet is one of the four types shown in the figure below, its parameters are compared with parameters in the nat/ip forwarding table. if one of the entries matches it, this device performs nat/ip forwarding after removing the pppoe header or v6 over v4 tunnel header by hardware. when it is required to add one of the four kinds of headers shown in the figure below after performing nat/ip forwarding, it is necessary for the pppoe header field, the v4 tunnel header field, the control bit field in the nat/ ip forwarding table to be specified appropriately. also, the pppoe header register or v4 tunnel header has to be set properly. the packet length is not checked after these headers are added. if the original packet length is long enough, the output packet may be larger than the desired mtu of the connection. to prevent this situation, the mtu value of the packets that will be received by this device that are transmitted by the networking device must be set carefully. only ip packets can be processed by hardware. lcp and ipcp packet sent during the pppoe discovery or session stages are sent to the host through the host interface block. packet formats supported by header processing function ipv6 over ipv4 ipv6 over pppoe ipv4 over pppoe ipv6 over ipv4 over pppoe ether header ipv4 tunnel header ipv6 header data (tcp/udp) crc ether header pppoe header ppp header ipv6 header data (tcp/udp) crc ether header pppoe header ppp header ipv4 header data (tcp/udp) crc ether header pppoe header ppp header ipv4 tunnel header ipv6 header data (tcp/udp) crc
mb86977 13 3. fef engine-filtering function filtering filtering can be applied to packets that are forwarded between differing segments, i.e. the d.m.z. and lan, the d.m.z. and wan, and the wan and lan segments. filtering is executed based on the following information. ? protocol type (type field in ethernet) ? ip address ? tcp/udp port number ? icmp message type there are two filters, one for inbound packets, and the other for outbound packets.a maximum of 64 entries can be set per filter. filtering can be applied to both ipv4 and ipv6 packets. filtering can also be executed on packets that include ip frames such as pppoe session stage packets. in addition, filtering can also be applied to the l3/ l4 information of ah packets, and the ip addresses of esp type ipsec packets. the relation between the filter and fef is shown in nat/ip forwarding function overview. when the host interface block receives a packet from the switch block, it is first checked by the rx filter and then forwarded to the nat/ip forwarding block. the tx filter is applied after the packet has been processed by the nat/ip forwarding block. filter logging this device can record several characteristics of the packets dropped by the filters. there are counters that can record the number of packets dropped, and buffers that can store the first 60 bytes of up to four packets that were dropped by the filters. each of the 64 filter table entries (for both the input and output filters) has a counter that can count up to 255. if the counter overflows, it is informed to the host by asserting an interrupt signal. the host may poll the counter instead if required. the buffers that store the headers of the packets (i.e. the first 60 bytes of the packet) can be configured to have the packets that match the condition (1) constantly overwrite the previously stored packet data, or (2) not overwrite the previously stored packets but assert the interrupt signal as soon as all four buffers have been occupied.
mb86977 14 4. fef engine-priority control function priority control can be applied to d.m.z. and wan connections through the cooperation of the fef engine, priority queues in the switch block, and the classifier block. priority control is best recommended for applications such as voip where small jitter and minimal delay are required. the switch block forms both high and low priority queues as shown in the figure below. the low priority queue is used for the transmission of packets with normal priority such as data packets. the high priority queue is used for applications such as voip where high trans- mission quality is required. the classifier block determines the priority of an ip packet by referring the fields of the packet to the corresponding settings in the priority control table. below explains the operation of the classifier block when a packet is transmitted from the d.m.z. to wan. first, the classifier block defines the priority of the packet received at the d.m.z. interface.if the packet is classified as high priority, the packet is linked to the high priority queue destined for the host interface block. the high priority queue is serviced prior to the low priority queue, and fef processing is carried out on the packet. since in this case the nat/ip forwarding table has defined the wan high priority interface as the packet destination, the fef will process the packet and link it to the high priority queue destined for the wan. this wan high priority queue will be serviced at top priority.packet transmission from the wan to the d.m.z. interface is also performed in the same manner. priority control in the packet transmission from d.m.z. to wan. dmz input ports dmz output ports high priority queue classifier @d.m.z port low priority queue fef engine high priority queue low priority queue wan input ports wan output ports classifier @wan port wab interface side queue host interface side queue
mb86977 15 5. l2 switch function the l2 switching is possible by the mac address base between ports for lan. the processing of fef is not needed in the same segment, and the processing load of fef reduced.
mb86977 16 n electrical characteristics 1. absolute maximum ratings (v ss = 0 v) *1 : 1.8 v *2 : 3.3 v warning: semiconductor devices can be permanently damaged by application of stress (voltage, current, temperature, etc.) in excess of absolute maximum ratings. do not exceed these ratings. 2. recommended operating conditions warning: the recommended operating conditions are required in order to ensure the normal operation of the semiconductor device. all of the devices electrical characteristics are warranted when the device is operated within these ranges. always use semiconductor devices within their recommended operating condition ranges. operation outside these ranges may adversely affect reliability and could result in device failure. no warranty is made with respect to uses, operating conditions, or combinations not represented on the data sheet. users considering application outside the listed conditions are advised to contact their fujitsu representatives beforehand. parameter symbol rating unit min max power supply voltage v ddi * 1 v ss - 0.5 + 2.5 v v dde * 2 v ss - 0.5 + 4.0 v input voltage v i v ss - 0.5 v dde + 0.5 v output voltage v o v ss - 0.5 v dde + 0.5 v storage temperature t stg - 55 + 125 c operation junction temperature t j - 40 + 125 c output current i o - 4 + 4ma parameter symbol value unit min typ max power supply voltage v ddi 1.65 1.8 1.95 v v dde 3.0 3.3 3.6 v h level input voltage v ih 2.0 ? v dde + 0.3 v l level input voltage v il - 0.3 ? 0.8 v operating temperature ta - 20 ? 85 c
mb86977 17 3. dc characteristics (v dde = 3.3 v 0.3 v, v ddi = 1.8 v 0.15 v, v ss = 0 v, ta = - 20 c to + 85 c) * : refer to the figures below. parameter symbol conditions value unit min typ max power supply current i dd operation state ? 450 700 ma i dds static state ?? 10 ma h level output voltage v oh h level output current i oh = - 100 m a v dde - 0.2 ? v dde v l level output voltage v ol l level output current i ol = - 100 m a 0 ? 0.2 v h level output v-i characteristics ? v dde = 3.3 v 0.3 v * ? l level output v-i characteristics ? v dde = 3.3 v 0.3 v * ? input leak current i l ? - 5 ? + 5 m a min min ty p ty p max max v oh - v dde (v) v ol (v) i oh (ma) i ol (ma) 0.0 - 1.0 - 2.0 - 3.0 - 4.0 4.0 3.0 2.0 1.0 0.0 0 - 20 - 40 - 60 - 80 - 100 - 120 120 100 80 60 40 20 0 l level output v-i characteristics h level output v-i characteristics
mb86977 18 4. ac characteristics (1) host interface data read timing (v dde = 3.3 v 0.3 v, v ddi = 1.8 v 0.15 v, v ss = 0 v, ta = - 20 c to + 85 c) parameter symbol value unit min typ max chip select input setup time t 1 5 ?? ns chip select input hold time t 2 5 ?? ns read enable input setup time t 3 5 ?? ns read enable input hold time t 4 5 ?? ns address input setup time t 5 5 ?? ns address input hold time t 6 5 ?? ns read data output delay time t 7 ?? 42 ns read data output hold time t 8 ?? 42 ns t1 t6 t4 t2 t5 t3 t8 t7 sclk cs_ we_ re_ a [13:2] dq [31:0] cs_ or re_, whichever happens later cs_ or re_, whichever happens later
mb86977 19 (2) host interface data write timing (v dde = 3.3 v 0.3 v, v ddi = 1.8 v 0.15 v, v ss = 0 v, ta = - 20 c to + 85 c) parameter symbol value unit min typ max chip select input setup time t 1 5 ?? ns chip select input hold time t 2 5 ?? ns write enable input setup time t 3 5 ?? ns write enable input hold time t 4 5 ?? ns address input setup time t 5 5 ?? ns address input hold time t 6 5 ?? ns write data input setup time t 7 5 ?? ns write data input hold time t 8 5 ?? ns sclk cs_ we_ re_ a [13:2] dq [31:0] t1 t6 t4 t2 t5 t3 t8 t7
mb86977 20 (3) host interface interrupt timing (v dde = 3.3 v 0.3 v, v ddi = 1.8 v 0.15 v, v ss = 0 v, ta = - 20 c to + 85 c) parameter symbol value unit min typ max interrupt signal output delay time t 1 ?? 15 ns sclk int_ t1 t1
mb86977 21 (4) reset timings (v dde = 3.3 v 0.3 v, v ddi = 1.8 v 0.15 v, v ss = 0 v, ta = - 20 c to + 85 c) parameter symbol value unit min typ max reset assert time t 1 5 ?? clock cycle access barred time after reset deassertion t 2 1000 ?? clock cycle sclk srst_ t1 t2
mb86977 22 (5) mii interface data transmission timing (v dde = 3.3 v 0.3 v, v ddi = 1.8 v 0.15 v, v ss = 0 v, ta = - 20 c to + 85 c) parameter symbol value unit min typ max tx_en output delay time t 1 ?? 20 ns txd output delay time t 2 ?? 20 ns tx_clk tx_en txd [3:0] tx_clk tx_en txd [3:0] t1 t2 t1 t2 x x55 n n - 1
mb86977 23 (6) mii interface data reception timing (v dde = 3.3 v 0.3 v, v ddi = 1.8 v 0.15 v, v ss = 0 v, ta = - 20 c to + 85 c) parameter symbol value unit min typ max rx_dv input setup time t 1 3 ?? ns rx_dv input hold time t 2 3 ?? ns rxd input setup time t 3 3 ?? ns rxd input hold time t 4 3 ?? ns rx_er input setup time t 5 3 ?? ns rx_er input hold time t 6 3 ?? ns rx_clk rx_dv rxd [3:0] rx_clk rx_dv rxd [3:0] rx_clk rx_er t1 t1 t3 t3 55 n n - 1 t2 t2 t4 t4 t6 t5 t5 t6 0 0
mb86977 24 (7) smi interface (v dde = 3.3 v 0.3 v, v ddi = 1.8 v 0.15 v, v ss = 0 v, ta = - 20 c to + 85 c) parameter symbol value unit min typ max smi data input setup time t 1 20 ?? ns smi data input hold time t 2 20 ?? ns smi data output delay time t 3 ?? 100 ns smi turn-on delay time (input mode ? output mode) t 4 ?? 100 ns smi turn-off delay time (output mode ? input mode) t 5 ?? 100 ns mdc mdio (input) mdc mdio (input output) mdc mdio (output) mdc mdio (output input) t1 t1 t3 t3 t2 t2 t4 t5 output mode output mode input mode input mode
mb86977 25 (8) rmii interface (v dde = 3.3 v 0.3 v, v ddi = 1.8 v 0.15 v, v ss = 0 v, ta = - 20 c to + 85 c) parameter symbol value unit min typ max rxd input setup time t 1 4 ?? ns rxd input hold time t 2 4 ?? ns crs_dv input setup time t 3 4 ?? ns crs_dv input hold time t 4 4 ?? ns tx_en output delay time t 5 ?? 15 ns txd output delay time t 6 ?? 15 ns ref_clk crs_dv rxd [1:0] ref_clk tx_en ref_clk crs_dv t1 t3 t2 t4 t5 t5 t6 rxd [1:0] txd [1:0]
mb86977 26 n system configuration rj45 rj45 rj45 rj45 4 port 10/100 m ethernet trv mb86977 mpu flash address bus data bus ram
mb86977 27 n notes on hardware setting this section describes the sequence of on/off of the power supply. though the sequence of on/off is not restricted, the following sequences are recommended. power-on sequence: 1) vddi 2) vdde 3) signal power-off sequence: 1) signal 2) vdde 3) vddi notes : vdde should not be supplied with signals while vddi is off; otherwise a through current may flow, causing potential reliability problems of the lsi. when switching vdde from off to on, it is possible that the internal state of the circuit is not be maintained due to power source noises. therefore, the circuit should be initialized. the circuit should be initialized after power-on.
mb86977 28 n ordering information part number package remarks MB86977PFV-G-BND 208 - pin plastic lqfp (fpt-208p-m06)
mb86977 29 n package dimension 208-pin plastic lqfp (fpt-208p-m06) note 1) * : these dimensions do not include resin protrusion. note 2) pins width and pins thickness include plating thickness. note 3) pins width do not include tie bar cutting remainder. dimensions in mm (inches) note : the values in parentheses are reference values. c 2003 fujitsu limited f208027s-c-3-3 details of "a" part 0.25(.010) (stand off) (.004.002) 0.100.05 (.024.006) 0.600.15 1.50 +0.20 C0.10 +.008 C.004 .059 0 ? ~8 ? "a" 0.08(.003) (.006.002) 0.1450.055 index 1 lead no. 52 53 104 105 156 157 208 0.50(.020) 0.08(.003) m (.009.002) 0.220.05 28.000.10(1.102.004)sq 30.000.20(1.181.008)sq (mounting height) *
mb86977 fujitsu limited all rights reserved. the contents of this document are subject to change without notice. customers are advised to consult with fujitsu sales representatives before ordering. the information, such as descriptions of function and application circuit examples, in this document are presented solely for the purpose of reference to show examples of operations and uses of fujitsu semiconductor device; fujitsu does not warrant proper operation of the device with respect to use based on such information. when you develop equipment incorporating the device based on such information, you must assume any responsibility arising out of such use of the information. fujitsu assumes no liability for any damages whatsoever arising out of the use of the information. any information in this document, including descriptions of function and schematic diagrams, shall not be construed as license of the use or exercise of any intellectual property right, such as patent right or copyright, or any other right of fujitsu or any third party or does fujitsu warrant non-infringement of any third-partys intellectual property right or other right by using such information. fujitsu assumes no liability for any infringement of the intellectual property rights or other rights of third parties which would result from the use of information contained herein. the products described in this document are designed, developed and manufactured as contemplated for general use, including without limitation, ordinary industrial use, general office use, personal use, and household use, but are not designed, developed and manufactured as contemplated (1) for use accompanying fatal risks or dangers that, unless extremely high safety is secured, could have a serious effect to the public, and could lead directly to death, personal injury, severe physical damage or other loss (i.e., nuclear reaction control in nuclear facility, aircraft flight control, air traffic control, mass transport control, medical life support system, missile launch control in weapon system), or (2) for use requiring extremely high reliability (i.e., submersible repeater and artificial satellite). please note that fujitsu will not be liable against you and/or any third party for any claims or damages arising in connection with above-mentioned uses of the products. any semiconductor devices have an inherent chance of failure. you must protect against injury, damage or loss from such failures by incorporating safety design measures into your facility and equipment such as redundancy, fire protection, and prevention of over-current levels and other abnormal operating conditions. if any products described in this document represent goods or technologies subject to certain restrictions on export under the foreign exchange and foreign trade law of japan, the prior authorization by japanese government will be required for export of those products from japan. f0311 ? fujitsu limited printed in japan

▲Up To Search▲

Price & Availability of MB86977PFV-G-BND

	To Download MB86977PFV-G-BND Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .